Download account with shared data plan

ABSTRACT

A device is configured to create an account including a plurality of members and a shared data plan. The device stores a content associated with the account and the shared data plan is set up to be charged for data used on an operating network to provide the content to the plurality of members associated with a plurality of operator networks. Further, the device provides the content to a user device associated with a member of the plurality of members. The content is provided through the operator network. The device charges the shared data plan for the amount of data used by the operator network to provide the content to the user device without causing a data plan between the member and the operator network to be charged for the amount of data.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/107,142, filed Dec. 16, 2013, which is incorporated herein byreference.

BACKGROUND

User devices, such as smart phones, often use operator networks todownload content. For example, a user device may have a data plan withan operator network allowing the user device to download data from theInternet. However, the operator network may charge the user's data planbased on the amount of data downloaded.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flowchart of an example process for creating and storing adownload account;

FIG. 5 is a flowchart of an example process of authenticating a memberof the download account;

FIG. 6 is a flowchart of an example process of providing content to amember of the download account and charging a shared data plan for thedata used to provide the content; and

FIGS. 7A and 7B are diagrams of an example implementation 700 relatingto the process shown in FIG. 6.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

People often use user devices (e.g., phones, tablets, etc.) to sharepictures, videos, and other content taken at an event (e.g., a wedding,a photo shoot, etc.). Further, people often use user devices to downloadcontent from commercial entities. A person may rely on an operatornetwork to download this media-rich content. However, the person mayincur a data charge for downloading the content over the operatornetwork, which may be taxing on the person's data plan. Accordingly, aperson may be discouraged from downloading the content over the operatornetwork. Implementations described herein allow members of a downloadaccount to download content over one or more operator networks using ashared data plan without a member's operator network data plan (e.g., apre-paid or a post-paid plan) being charged for data used to provide thecontent over the member's operator network.

FIG. 1 is a diagram illustrating an overview of an exampleimplementation 100 described herein.

In example implementation 100, assume an account creator (i.e., anaccount owner) requests a server device to create a download account.Assume the download account allows members to share a data plan todownload content associated with the download account over an operatornetwork A and an operator network B. Further, assume that the serverdevice has an agreement A with operator network A to pay for data usedover operator network A, and that the server device has an agreement Bwith operator network B to pay for data used over operator network B.

As shown in FIG. 1, a first member of the download account may use auser device (“user device A”) to transmit a request for the contentassociated with the download account to the server device via operatornetwork A. The server device may receive the request, obtain the contentassociated with the download account, and provide the content tooperator network A for transmission to the user device. Operator networkA may provide the content to the user device without charging a dataplan that the first member has with operator network A. Rather, operatornetwork A may charge an owner of the server device for the data used toprovide the content to the user device according to agreement A.Operator network A may then inform the server device of the data chargeaccording to agreement A.

Likewise, a second member of the download account may use a user device(“user device B”) to transmit a request for the content associated withthe download account to the server device via operator network B. Theserver device may receive the request, obtain the content associatedwith the download account, and provide the content to operator network Bfor transmission to the user device. Operator network B may provide thecontent to the user device without charging a data plan that the secondmember has with operator network B. Rather, operator network B maycharge the owner of the server device for the data used to provide thecontent to the user device according to agreement B. Operator network Bmay then inform the server device of the data charge according toagreement B.

The server device may charge the account owner by charging the shareddata plan for the account for the data used to provide the content tothe first member and the second member based on the data charged toagreements A and B. For example, an amount of data remaining in theshared data plan may be updated based on the data used by the firstmember and the second member.

In this way, members of the download account may download the contentover different operator networks using a shared data plan and withoutthe members' operator network data plans being charged. At the sametime, the operator networks may still be paid by the account owner forthe data used to transmit the content to the member. Moreover, theserver device may make it easier, cheaper, and more desirable formembers to download the content associated with the download account.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,environment 200 may include an operator network 210. The operatornetwork 210 may include a base station 220, a serving gateway 230(hereinafter referred to as “SGW 230”), a mobility management entitydevice 240 (hereinafter referred to as “MME 240”), a packet data network(PDN) gateway 250 (hereinafter referred to as “PGW 250”), a homesubscriber server (HSS)/authentication, authorization, accounting (AAA)server 260 (hereinafter referred to as “HSS/AAA server 260”), and a callsession control function (CSCF) server 265 (hereinafter referred to as“CSCF server 265”). Environment 200 may also include a user device 270,a server device 280, a storage device 290, and a network 295.

Operator network 210 may include an evolved packet system (EPS) thatincludes a long term evolution (LTE) network and/or an evolved packetcore (EPC) that operate based on a third generation partnership project(3GPP) wireless communication standard. The LTE network may be a radioaccess network (RAN) that includes one or more base stations, such aseNodeBs (eNBs), via which user device 270 communicates with the EPC. TheEPC may include SGW 230, MME 240, and/or PGW 250 that enables userdevice 270 to communicate with network 295 and/or an Internet protocol(IP) multimedia subsystem (IMS) core. The IMS core may include HSS/AAAserver 260 and/or CSCF server 265 and may manage certain information andservices, such as authentication, session initiation, accountinformation, and/or a user profile, associated with user device 270. TheLTE network may include multiple base stations 220, and the EPC mayinclude multiple SGWs 230, MMEs 240, and/or PGWs 250. Additionally, oralternatively, operator network 210 may include a cellular network, apublic land mobile network (PLMN), a second generation (2G) network, athird generation (3G) network, a fourth generation (4G) network, a fifthgeneration (5G) network, and/or another network.

Base station 220 may include one or more network devices that receive,process, and/or transmit traffic, such as audio, video, text, and/orother data, destined for and/or received from user device 270. In anexample implementation, base station 220 may be an eNB device and may bepart of the LTE network. Base station 220 may receive traffic fromand/or send traffic to network 295 via SGW 230 and PGW 250. Base station220 may send traffic to and/or receive traffic from user device 270 viaan air interface. One or more of base stations 220 may be associatedwith a RAN, such as the LTE network.

SGW 230 may include one or more network devices, or other types ofcomputation or communication devices, that gather, process, search,store, and/or provide information in a manner described herein. SGW 230may include one or more data processing and/or traffic transfer devices,such as a gateway, a router, a modem, a switch, a firewall, a networkinterface card (NIC), a hub, a bridge, a proxy server, an opticaladd-drop multiplexer (OADM), or some other type of device that processesand/or transfers traffic. SGW 230 may, for example, aggregate trafficreceived from one or more base stations 220 and may send the aggregatedtraffic to network 295 via PGW 250. In one example implementation, SGW230 may route and forward user data packets, may act as a mobilityanchor for a user plane during inter-base station handovers, and may actas an anchor for mobility between LTE and other 3GPP technologies.

MME 240 may include one or more computation or communication devicesthat gather, process, search, store, and/or provide information in amanner described herein. For example, MME 240 may perform operationsassociated with a handoff to and/or from the EPS. MME 240 may performoperations to register user device 270 with the EPS, to handoff userdevice 270 from the EPS to another network, to handoff user device 270from the other network to the EPS, and/or to perform other operations.MME 240 may perform policing operations for traffic destined for and/orreceived from user device 270.

PGW 250 may include one or more network devices that gather, process,search, store, and/or provide information in a manner described herein.PGW 250 may include one or more data processing and/or traffic transferdevices, such as a gateway, a router, a modem, a switch, a firewall, aNIC, a hub, a bridge, a proxy server, an OADM, or some other type ofdevice that processes and/or transfers traffic. PGW 250 may, forexample, provide connectivity of user device 270 to external packet datanetworks by being a traffic exit/entry point for user device 270. PGW250 may perform policy enforcement, packet filtering, charging support,lawful intercept, and packet screening. PGW 250 may also act as ananchor for mobility between 3GPP and non-3GPP technologies. PGW 250 mayauthenticate user device 270 (e.g., via interaction with HSS/AAA server260).

HSS/AAA server 260 may include one or more server devices, or othertypes of computation or communication devices, that gather, process,search, store, and/or provide information in a manner described herein.For example, HSS/AAA server 260 may manage, update, and/or store, in amemory associated with HSS/AAA server 260, profile informationassociated with user device 270 that identifies applications and/orservices that are permitted for and/or accessible by user device 270,bandwidth or data rate thresholds associated with the applications orservices, information associated with a user of user device 270 (e.g., ausername, a password, a personal identification number (PIN), etc.), adata plan, rate information, minutes allowed, and/or other information.Additionally, or alternatively, HSS/AAA server 260 may include a devicethat performs authentication, authorization, and/or accounting (AAA)operations associated with a communication session with user device 270.With regard to the authentication operation, HSS/AAA server 260 mayverify a device's (e.g., user device 270) specific digital identityprovided via an identifier (e.g., a password, a digital certificate, aphone number, etc.) associated with the device. With regard to theauthorization function, HSS/AAA server 260 may grant or refuseprivileges to a device (e.g., user device 270) for accessing specificservices (e.g., IP address filtering, address assignment, routeassignment, quality of service (QoS), etc.). With regard to theaccounting operation, HSS/AAA server 260 may track consumption ofnetwork resources (e.g., by user device 270) and may use thisinformation for management, planning, billing, etc.

CSCF server 265 may include one or more server devices, or other typesof computation or communication devices, that gather, process, search,store, and/or provide information in a manner described herein. CSCFserver 265 may process and/or route calls to and from user device 270via the EPC. For example, CSCF server 265 may process calls, receivedfrom network 295, that are destined for user device 270. In anotherexample, CSCF server 265 may process calls, received from user device270, that are destined for network 295.

CSCF server 265 may also include a policy and charging rules function(PCRF) that may perform operations that enforce EPS policies associatedwith a communication session with user device 270. For example, the PCRFmay dynamically provide real-time bandwidth allocations and/or controls(e.g., associated with a particular access point name (APN)) associatedwith particular applications, network accesses, and/or services providedto user device 270 during a communication session. The PCRF may alsodynamically provide a real-time signal flow policy to adapt to changingconditions within the network and/or to manage traffic flow during thecommunication session.

User device 270 may include any computation or communication device,such as a communication device that is capable of communicating with anetwork (e.g., network 295) and/or an operator network (e.g., operatornetwork 210). For example, user device 270 may include a radiotelephone,a personal communications system (PCS) terminal (e.g., that may combinea cellular radiotelephone with data processing and data communicationscapabilities), a personal digital assistant (PDA) (e.g., that caninclude a radiotelephone, a pager, Internet/intranet access, etc.), asmart phone, a computer, a laptop, a tablet computer, a server, a, acamera, a gaming device, or another mobile, computation, orcommunication device.

Server device 280 may include one or more server devices, or other typesof computational or communication devices, that gather, process, search,store, and/or provide information in a manner described herein. Serverdevice 280 may manage connections (e.g., virtual private network (VPN)connections) with PGWs 250 included in one or more operator networks210. Server device 280 may be part of operator network 210, or may be anexternal device to operator network 210. In an example implementation,server device 280 may be operated by an operator of operator network210. Additionally, or alternatively, server device 280 may include acommunication interface that allows server device 280 to receiveinformation from and/or transmit information to other devices inenvironment 200.

Storage device 290 may include one or more devices capable of storingand/or searching content and/or a data structure (e.g., a database). Insome implementations, storage device 290 may include a communicationinterface that allows storage device 290 to receive information fromand/or transmit information to other devices in environment 200.

Network 295 may include one or more wired and/or wireless networks. Forexample, network 270 may include a cellular network, a public landmobile network (PLMN), a second generation (2G) network, a thirdgeneration (3G) network, a fourth generation (4G) network, a fifthgeneration (5G) network, and/or another network. Additionally, oralternatively, network 270 may include a wide area network (WAN), ametropolitan network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PTSSN)), an ad hoc network, an intranet, theInternet, a fiber optic-based network, and/or combination of these orother types of networks.

The number of devices and/or networks shown in FIG. 2 is provided forexplanatory purposes. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oneor more of the devices of environment 200 may perform one or morefunctions described as being performed by another one or more devices ofenvironment 200. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to base station 220, SGW 230, MME 240, PGW 250, HSS/AAAserver 260, CSCF server 265, user device 270, server device 280, and/orstorage device 290. Alternatively, or additionally, each of base station220, SGW 230, MME 240, PGW 250, HSS/AAA server 260, CSCF server 265,user device 270, server device 280, and/or storage device 290 mayinclude one or more devices 300 and/or one or more components of device300.

As shown in FIG. 3, device 300 may include a bus 310, a processor 320, amemory 330, an input component 340, an output component 350, and acommunication interface 360. In other implementations, device 300 maycontain fewer components, additional components, different components,or differently arranged components than depicted in FIG. 3.Additionally, or alternatively, one or more components of device 300 mayperform one or more tasks described as being performed by one or moreother components of device 300.

Bus 310 may include a path that permits communication among thecomponents of device 300. Processor 320 may include one or moreprocessors, microprocessors, or processing logic that interpret andexecute instructions. Memory 330 may include any type of dynamic storagedevice that stores information and instructions, for execution byprocessor 320, and/or any type of non-volatile storage device thatstores information for use by processor 320.

Input component 340 may include a mechanism that permits a user to inputinformation to device 300, such as a keyboard, a keypad, a button, aswitch, etc. Output component 350 may include a mechanism that outputsinformation to the user, such as a display, a speaker, one or more lightemitting diodes (LEDs), etc.

Communication interface 360 may include any transceiver-like mechanismthat enables device 300 to communicate with other devices and/orsystems. For example, communication interface 360 may include anEthernet interface, an optical interface, a coaxial interface, awireless interface, or the like.

In another implementation, communication interface 360 may include, forexample, a transmitter that may convert baseband signals from processor320 to radio frequency (RF) signals and/or a receiver that may convertRF signals to baseband signals. Alternatively, communication interface360 may include a transceiver to perform functions of both a transmitterand a receiver of wireless communications (e.g., radio frequency,infrared, visual optics, etc.), wired communications (e.g., conductivewire, twisted pair cable, coaxial cable, transmission line, fiber opticcable, waveguide, etc.), or a combination of wireless and wiredcommunications. Communication interface 360 may connect to an antennaassembly (not shown in FIG. 3) for transmission and/or reception of theRF signals.

The antenna assembly may include one or more antennas to transmit and/orreceive RF signals over the air. The antenna assembly may, for example,receive RF signals from communication interface 360 and transmit the RFsignals over the air, and receive RF signals over the air and providethe RF signals to communication interface 360. In one implementation,for example, communication interface 360 may communicate with operatornetwork 210, devices connected to operator network 201, network 295,and/or devices connected to network 295.

Device 300 may perform various operations described herein. Device 300may perform these operations in response to processor 320 executingsoftware instructions included in a computer-readable medium, such asmemory 330. A computer-readable medium is defined as a non-transitorymemory device. A memory device includes memory space within a singlestorage device or memory space spread across multiple storage devices.

Software instructions may be read into memory 330 from anothercomputer-readable medium or from another device via communicationinterface 360. When executed, software instructions stored in memory 330may cause processor 320 to perform one or more processes describedherein. Additionally, or alternatively, hardwired circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

The number of components shown in FIG. 3 is provided for explanatorypurposes. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3.

FIG. 4 is a flowchart of an example process 400 for creating and storinga download account. The download account may allow members to share adata plan and download content associated with the download accountusing the shared data plan.

In some implementations, one or more process blocks of FIG. 4 may beperformed by server device 280. Additionally, or alternatively, one ormore process blocks of FIG. 4 may be performed by another device orgroup of devices separate from or including server device 280.

As shown in FIG. 4, process 400 may include creating a download account(block 410). For example, server device 280 may create the downloadaccount.

In some implementations, an account creator (e.g., a user) may use userdevice 270 or another device to send a request to create the downloadaccount to server device 280. Server device 280 may receive the requestand create the download account by generating an entry in an accountdata structure for the download account. Server device 280 may createmultiple download accounts and may generate an entry in the account datastructure for each download account. The account data structure may bestored in storage device 290 and/or a memory of server device 280.Server device 280 may grant the account creator administrative rights tomanage or change the account.

As further shown in FIG. 4, process 400 may include obtaining memberinformation on a member of the download account (block 420). Forexample, server device 280 may obtain the member information.

The account creator may identify a member of the download account byinputting member information for the member into user device 270 oranother device. User device 270 or the other device may send the memberinformation to server device 280, and server device 280 may receive themember information. The account creator may identify more than onemember of the download account and server device 280 may receive memberinformation for more than one member.

The member information may include information related to a member ofthe download account. For example, the member information may includemember identification information that identifies a member, such as aname and/or a member identification (“ID”). The member information mayinclude contact information that may be used to contact the member, suchas an email address and/or a phone number. The member information mayinclude device information identifying one more user devices 270associated with the member. For example, the device information mayinclude a user device ID, a phone number, an IP address, aninternational mobile subscriber identity (“IMSI”), an internationalmobile station equipment identity (“IMEI”), a mobile equipmentidentifier (“MEID”), or the like. The member information may alsoinclude operator information indicating an operator network 210associated with the member. For example, the member information mayindicate a member's subscription or affiliation with an operator network210.

The account creator may not know all of the member information and maynot be able to input this information into user device 270 fortransmission to server device 280. For example, the account creator maynot know a member's device information and operator information.Accordingly, in some implementations, the member may use a user device270 to transmit this information to server device 280. For example, themember may use user device 270 to connect to server device 280. Datapackets sent from user device 270 via the operator network may indicatethe device information (e.g., the IMSI) and an operator network 210affiliated with user device 270. Additionally, or alternatively, themember may input the device information and operator information intouser device 270, and transmit the device information and operatorinformation to server device 280. In some implementations, some of themember information may be obtained when the member is authenticated asshown in FIG. 5.

Server device 280 may store the member information in the account datastructure for the download account.

As further shown in FIG. 4, process 400 may include associating contentwith the download account (block 430). For example, server device 280may associate the content with the download account.

An account owner, the account creator, and/or another member may useuser device 270 to upload content to server device 280. Server device280 may store the content and associate the content with the downloadaccount. Server device 280 may store the content in storage device 290and/or in a memory of server device 280.

The content may be any kind of data. For example, the content may be oneor more videos, audio files, photos, documents, applications, programs,or the like.

Server device 280 may store information identifying the content and alocation where the content can be obtained from the account datastructure.

As further shown in FIG. 4, process 400 may include generating an accesspoint identifier for the download account (block 440). For example,server device 280 may generate the access point identifier.

The access point identifier may identify an access point associated withthe download account that may be used by operator network 210 totransmit data between user device 270 and server device 280. Forexample, the access point identifier may include an APN ID associatedwith an APN for the download account. The APN is a name of a gatewaythat operator network 210 (e.g., PGW 250) may use to transmit databetween user device 270 and server device 280.

Server device 280 may generate an access point identifier for eachdownload account in the account data structure. The access pointidentifier for each download account may be stored in the account datastructure. In some implementations, server device 280 may generate adifferent access point identifier for each operator network, a differentaccess point identifier for each member, and/or a different access pointidentifier for each member per operator network.

As further shown in FIG. 4, process 400 may include providing the accesspoint identifier to operator network 210 (block 450). For example,server device 280 may provide the access point identifier to operatornetwork 210. Operator network 210 may create a new access point at PGW250 that is identified by the access point identifier. For example,operator network may create a new APN at PGW 250. Accordingly, operatornetwork 210 may use the new access point at PGW 250 to connect userdevice 270 and server device 280.

Server device 280 may provide the access point identifier to more thanone operator network 210. For example, server device 280 may provide theaccess point identifier to each operator network 210 affiliated with amember of the download account.

As further shown in FIG. 4, process 400 may include establishing anaccount data plan, associated with the access point identifier, withoperator network 210 (block 460). For example, server device 280 mayestablish the account data plan with operator network 210. Server device280 may instruct operator network 210 to charge the account data planfor data transmitted over the access point at PGW 250 identified by theaccess point identifier.

In some implementations, server device 280 may instruct operator network210 to charge the account data plan for all data transmitted over theaccess point. Additionally, or alternatively, server device 280 mayinstruct operator network to charge the account data plan for only someof the data transmitted over the access point. For example, serverdevice 280 may instruct operator network 210 to charge the account dataplan for a certain percentage or a certain amount of data transmittedover the access point. Operator network 210 may charge a remainingpercentage or amount to an operator network data plan associated withuser device 270.

Server device 280 may establish an account data plan with more than oneoperator network 210. For example, server device 280 may establish anaccount data plan with each operator network 210 affiliated with amember of the download account. Accordingly, server device 280 may havean account data plan A with operator network A and an account data planB with operator network B.

Server device 280 may have an existing data plan or arrangement withoperator network 210 that may be used for the account data plan. Forexample, server device 280 may be operated by a network operator havingprior data agreements with other operator networks 210. The otheroperator networks 210 may charge the network operator for datatransmitted over the other operator networks using the access pointidentifier according to the prior agreements. Additionally, oralternatively, server device 280 may create a new data plan orarrangement with an operator network 210 that will be charged for datatransmitted over the access point identified by the access pointidentifier. The agreement(s) between server device 280 and operatornetwork(s) 210 may occur dynamically by active/dynamic negotiation.

As further shown in FIG. 4, process 400 may include generating a shareddata plan for the download account (block 470). For example, serverdevice 280 may generate the shared data plan.

Server device 280 may transmit information regarding a set of availableshared data plans to user device 270. The account creator may use userdevice 270 to select a shared data plan from the set of available shareddata plans. User device 270 may then transmit information on theselected shared data plan to server device 280 and server device 280 maygenerate the shared data plan for the download account based on theselected shared data plan.

The shared data plan may be a pre-paid data plan with a fixed amount ofdata usage (e.g., 10 gigabytes (GB), 50 GB, unlimited) that all themembers of the download account may use. Accordingly, the accountcreator may pay a fixed fee for the pre-paid data plan up front. Oncethe fixed amount of data has been used by the members, the downloadaccount may be terminated or the account creator may have the option ofadding more data to the shared data plan (possibly for a fee).

Additionally, or alternatively, the shared data plan may be a post-paiddata plan based on an actual amount of data used by the members overoperator networks 210. Accordingly, the account creator may pay a feedepending on how much data the members actually use over operatornetworks 210.

In some implementations, the shared data plan may or may not be used topay for all the data used to provide the content to a member.Accordingly, server device 280 may set an amount of data usage that theshared data plan will be used to pay for (e.g., all or some).Furthermore, server device 280 may set an amount of data usage that amember's operator network data plan will be used to pay for (e.g., noneor some).

For example, server device 280 may set that the shared data plan be usedto pay for all the data used by the members when downloading the contentassociated with the download account. Thus, when a member downloads thecontent associated with the download account, the shared data plan willbe charged for the data used over the operator network and the member'soperator network data plan will not be charged. In other words, thedownload account may be set up as a free download account where themembers may download the content without being charged for any datausage.

Additionally, or alternatively, server device 280 may set that theshared data plan is to be charged for a certain percentage or amount ofthe data used by the members. For example, when a member downloads thecontent associated with the download account, the shared data plan willbe charged for a percentage of the data used and the member's operatornetwork data plan will be charged for the remainder of the data used. Inother words, the download account may be set up as a reduced feedownload account where members may download the content for a reduceddata fee.

In some implementations, the shared data plan may be shared by themembers of the download account to pay for data used over multipleoperator networks 210. The shared data plan may be charged or updatedwhen an account data plan is charged by operator network 210 for datatransmitted using the access point identifier. For example, assumeserver device 280 establishes an account data plan A with operatornetwork A and establishes an account data plan B with operator networkB. When a member affiliated with operator network A downloads contentover operator network A using the access point identifier, operatornetwork A may charge account data plan A. Server device 280 may chargeor update the shared data plan according to the charge to account dataplan A. For instance, if operator network A charges data plan A for 1 GBof data, server device 280 may deduct 1 GB of data from the shared dataplan. Likewise, when a member affiliated with operator network Bdownloads content over operator network B using the access pointidentifier, operator network B may charge account data plan B. Serverdevice 280 may charge or update the shared data plan based on the chargeto account data plan B. For instance, if operator B charges data plan Bfor 2 GB of data, server device 280 may deduct 2 GB of data from theshared data plan. Thus, the shared data plan may have a total of 3 GB ofdata deducted based on the 1 GB used over operator network A and the 2GB used over operator network B. In this way, the shared data plan maybe used to pay for data used over multiple operator networks 210.

Server device 280 may store shared data plan information in the accountdata structure. The shared data plan information may include informationon the kind of shared data plan and a current status of the shared dataplan (e.g., an amount of data currently used by members or currentlyremaining in the shared data plan).

As further shown in FIG. 4, process 400 may include setting downloadaccount options (block 480). For example, server device 280 may set thedownload account options for the download account.

The account creator may input download account options into user device270, and user device 270 may transmit the download account options toserver device 280. Server device 280 may set the download accountoptions based on the account creator input.

In some implementations, to set the download account options, serverdevice 280 may set a limit on the amount of content associated with thedownload account. For example, the amount of content that may beuploaded by the account creator and/or by other members of the downloadaccount, and stored by server device 280 may be limited to a certainamount (e.g., 10 GB, 50 GB, unlimited, etc.).

In some implementations, to set the download account options, serverdevice 280 may set a time limit for the download account. For example,the download account may only be active for a certain length of timebefore being deactivated and/or deleted by server device 280.

In some implementations, to set the download account options, serverdevice 280 may restrict usage of the shared data plan between certaintime periods and/or certain locations. For example, server device 280may restrict members from using the shared data plan between certainhours of the day that may be peak times the operator networks 210 areused. The agreements between the operator networks 210 and server device280 may charge higher fees for data used during these peak times.

In some implementations, to set the download account options, serverdevice 280 may set restrictions on roaming for members. For example,operator network 210 may charge a higher price for data acquired whileroaming, and the account creator may not want to pay that higher price.Accordingly, server device 280 may allow members to download the contentwhile roaming or restrict members from downloading the content whileroaming.

In some implementations, to set the download account options, serverdevice 280 may apply limitations to one or more members of the downloadaccount and/or give administrative rights to one or more members.

For example, server device 280 may limit the amount of data each membermay use from the shared data plan. For instance, one member may beauthorized to download more data than another member.

Additionally, or alternatively, each member may only be authorized todownload certain content associated with the download account. In otherwords, each content associated with the download account may beassociated with a member or members that are permitted to download thecontent. For example, assume a photographer is the account creator andrequests server device 280 create a download account having thephotographer's clients as members. The photographer may specify whichpictures may be downloaded by which clients. Thus, each client may onlybe authorized to download pictures that the photographer authorized themto download, and the clients would not have access to pictures taken forother clients. Additionally, or alternatively, each member may beauthorized to download all the content associated with the downloadaccount. For example, consider a download account having the attendeesof a wedding as members. Further, assume the download account isassociated with pictures of the wedding. Each attendee may be authorizedto download all the pictures of the wedding.

Additionally, or alternatively, server device 280 may set what memberscan upload content to be associated with the download account based onthe account creator's input. In some implementations, only the accountcreator may be authorized to upload content. For example, if the accountcreator is a commercial entity (e.g., a photographer), the commercialentity may want to control what content is uploaded to the downloadaccount. In some implementations, one or members of the download accountmay be authorized to upload content. For example, if the downloadaccount is set up for members to share content with each other (e.g.,pictures taken by attendees at a wedding), each member may be authorizedto upload content to be associated with the download account.

Server device 280 may store the download account options in the accountdata structure.

Server device 280 may charge the account creator and/or anotherresponsible person for creating and managing the download account.Server device 280 may charge the account creator and/or the otherresponsible person for the download account in an amount that may dependon the shared data plan selected (e.g., an amount of data that can beused by the members over operator networks 210), and/or the downloadaccount options (e.g., an amount of content associated with the downloadaccount stored by server device 280). Thus, an account owner, an accountcreator, and/or another responsible person may pay for the account. Forexample, a sponsor my pay for the download account. The sponsor may bean advertiser that allows members to upload content to the account andmanage the account. However, the advertiser may add advertisements tothe content or transmit advertisements with the content when the contentis downloaded from the account.

While a series of blocks has been described with regard to FIG. 4, theblocks and/or the order of the blocks may be modified in someimplementations. Additionally, or alternatively, non-dependent blocksmay be performed in parallel.

FIG. 5 is a flowchart of an example process 500 of authenticating amember of the download account. In some implementations, one or moreprocess blocks of FIG. 5 may be performed by server device 280.Additionally, or alternatively, one or more process blocks of FIG. 5 maybe performed by another device or a group of devices separate from orincluding server device 280.

As shown in FIG. 5, process 500 may include requesting a member todownload an account application on user device 270 (block 510). Forexample, server device 280 may send a request to a member to downloadthe account application on user device 270.

Server device 280 may use the contact information for the member storedin the account data structure to send the request to the member. Therequest may include instructions on how to download and install theapplication. The request may also include a password to authenticate themember. The password may be a string of characters of any length. Therequest may ask the member to connect to the member's operator network210 to download the application. For example, the contact informationmay include an email address associated with the member. Server device280 may send an email to the email address requesting the member todownload the application on user device 270. Additionally, oralternatively, the member may use user device 270 to request theapplication. The member may then use user device 270 to download theapplication. In some implementations, server device 280 may provide theapplication to user device 270. Additionally, are alternatively, anotherdevice may provide the application to user device 270.

The account application may be used to authenticate the member. Forexample, the member may use the application to input memberidentification information, such as a member name, the contactinformation used to receive the request (e.g., an email address), and/ora password identified in the request to download the application. Theapplication may also gather other member information from user device270 (e.g., a user device ID, an operator affiliation, an IMSI, etc.).The application may use user device 270 to create a connection to serverdevice 280 and send the member information from user device 270 toserver device 280.

Additionally, or alternatively, the account application may be used byuser device 270 to obtain content from server device 280 afterauthentication is completed. This process will be discussed with regardsto FIG. 6.

As further shown in FIG. 5, process 500 may include receiving the memberinformation from user device 270 executing the account application(block 520). For example, server device 280 may receive the memberinformation from user device 270. In some implementations, the memberinformation may be received from third party services.

The member information received at block 520 may be added to the memberinformation received at block 420. For example, the account creator maynot have known or had access to a user device ID, an operator networkaffiliation, an IMSI, or the like that are associated with a member whencreating the download account. However, this unknown member informationmay be obtained at block 520 by server device 280 from user device 270executing the application. Accordingly, server device 280 may update theaccount data structure to include the member information obtained atblock 520.

Additionally, or alternatively, server device 280 may receive the membername, the contact information, and/or the password input by the memberinto the application via user device 270.

As further shown in FIG. 5, process 500 may include authenticating themember (block 530). For example, server device 280 may authenticate themember.

To authenticate the member, server device 280 may confirm that themember name, the contact information, and/or the password input by themember into the application and received by server device 280 matchesthe member information of the member the request was sent to and/ormatches the password included in the request sent by server device 280.

Once a member has been successfully authenticated, server device 280adds the member to a closed member authentication group. The closedmember authentication group includes members that have beenauthenticated and may access the content using the download account. Insome implementations, only authenticated members may use the applicationto access the content using the download account. Non-authenticatedmembers may not access the content.

In some implementations, once a member has been successfullyauthenticated, server device 280 may provide the access point identifierto user device 270 to be used by the account application. Accordingly,the account application on user device 270 may be mapped to the accesspoint identifier associated with the download account. In other words,user device 270 may use the account application to access the contentassociated with the download account using the access point identifiedby the access point identifier. Additionally, or alternatively, theaccount application may have included the access point identifier whendownloaded by user device 270.

As further shown in FIG. 5, process 500 may include providing the memberinformation of the member to operator network 210 (block 540). Forexample, server device 280 may provide the member information tooperator network 210.

Server device 280 may provide member information for an authenticatedmember to operator network 210 affiliated with the authenticated member.For example, server device 280 may provide a user device ID and/or anIMSI of user device 270 (e.g., user device 270 with the accountapplication installed) to the operator network 210. Server device 280may instruct operator network 210 that user device 270 is authorized touse the access point identified by the access point identifierassociated with download account. Operator network 210 may store themember information in a memory of HSS/AAA server 260. HSS/AAA server 260may associate the member information with information already storedabout the member in operator network 210 (e.g., a member's operatornetwork data plan with operator network 210). Accordingly, operatornetwork 210 may recognize that the member is authorized to use theaccess point to communicate with server device 280.

In some implantations, each operator network 210 may be provided withmember information corresponding to authenticated members that areaffiliated with operator network 210. The operator may store the memberinformation in a memory accessible by HSS/AAA server 260. Accordingly,when user device 270 attempts to connect to server device 280 throughoperator network 210, HSS/AAA server 260 may use the member informationto authenticate that user device 270 is authorized to use the accesspoint at the PGW.

While a series of blocks has been described with regard to FIG. 5, theblocks and/or the order of the blocks may be modified in someimplementations. Additionally, or alternatively, non-dependent blocksmay be performed in parallel.

FIG. 6 is a flowchart of an example process 600 of providing content toa member of the download account and charging a shared data plan for thedata used to provide the content. In some implementations, one or moreprocess blocks of FIG. 6 may be performed by operator network 210 and/orserver device 280. Additionally, or alternatively, one or more processblocks of FIG. 6 may be performed by another device or a group ofdevices separate from or including operator network 210 and/or serverdevice 280.

As shown in FIG. 6, process 600 may include receiving a request fromuser device 270 to obtain content associated with a download accountusing an access point identifier (block 605). For example, operatornetwork 210 may receive the request from user device 270.

A member of the download account may use the account applicationinstalled on user device 270 to generate a request for the contentassociated with the download account and stored by server device 280.The application may include the access point identifier in the request.The request may also include member information (e.g., a user deviceID). User device 270 may then transmit the request to operator network210 and operator network 210 may receive the request. Additionally, oralternatively, server device 280 may send the member and/or user device270 a message indicating content associated with the download account isavailable for download. For example, server device 280 may send anemail, an instant message, and/or a text message (e.g., a short messageservice (SMS) message and/or a multimedia messaging service (MMS)message) to the member including a link to download the content.Executing the link may generate the request and send the request tooperator network 210.

As further shown in FIG. 6, process 600 may include authenticating userdevice 270 (block 610). For example, operator network 210 mayauthenticate that user device 270 is authorized to receive data over aconnection on the access point identified by the access point identifierin the request. As previously discussed at block 540 (FIG. 5), serverdevice 280 may provide operator network 210 with information onauthenticated members allowed to use the access point associated withthe download account. Operator network 210 may carry out authenticationwith HSS/AAA server 260 using an AAA protocol and use the memberinformation to establish that user device 270 is authenticated to usethe access point to receive the content. For example, operator network210 may use a Diameter protocol to carry out authentication (e.g., aDiameter-Extensible Authentication Protocol (EAP)-Request and aDiameter-EAP-Answer).

In some implementations, operator network 210 may determine if userdevice 270 is roaming. In other words, operator network 210 maydetermine if user device 270 is affiliated with operator network 210 orif operator network 210 is acting as a roaming network that user device270 is visiting. User device 270 may use operator network 210 as aroaming network to download the content if operator network 210 has anappropriate agreement with a home network affiliated with user device270. Additionally, or alternatively, server device 280 may set up theaccess point associated with the download account with each of the homenetwork and the roaming network for user device 270 to use operatornetwork 210 as a roaming network. In some implementations, user device270 may use a different access point identifier in a roaming networkthan in a home network. Additionally, or alternatively, user device 270may have to be re-authenticated if user device 270 moves from a homenetwork to a roaming network.

As further shown in FIG. 6, process 600 may include transmitting therequest to server device 280 (block 615). For example, operator network210 may transmit the request to server device 280 over network 295.Operator network 210 may create a connection between user device 270 andserver device 280 using the access point identified by the access pointidentifier in the request. Operator network 210 may transmit the requestover the connection to the server device 280.

As further shown in FIG. 6 process 600 may include receiving the requestto provide content to user device 270 (block 620). For example, serverdevice 280 may receive the request from user device 270 via operatornetwork 210.

As further shown in FIG. 6, process 600 may include determining whetherthe content may be provided to user device 270 (block 625). For example,server device 280 may determine whether the content may be provided.

To determine whether the content may be provided, server device 280 maydetermine whether the member associated with user device 270 isauthorized to access the content. For example, server device 280 maycheck the account data structure to determine if the content isassociated with the member. If the content is not associated with themember, server device 280 may determine that the content may not beprovided to user device 270.

To determine whether the content may be provided, server device 280 maydetermine whether the member has reached a predetermined data limit. Forexample, the account creator may have set data limits for each member inthe download account. Server device 280 may check the account datastructure to determine if the member has reached the predetermined datalimit. If the member associated with user device 270 has reached thepredetermined data limit or does not have enough data left to downloadthe content, server device 280 may determine that the content may not beprovided to user device 270.

To determine whether the content may be provided, server device 280 maydetermine whether the shared data plan has reached a predetermined datalimit. For example, server device 280 may check the account datastructure to determine if there is enough data remaining in the shareddata plan to provide the content. If there is not enough data remainingin the shared data plan, server device 280 may determine that thecontent may not be provided to user device 270.

To determine whether the content may be provided, server device 280 maydetermine whether the download account has been terminated or exceededthe time limit set by the account creator. If the download account hasbeen terminated, server device 280 may determine that the content maynot be provided to user device 270.

To determine whether the content may be provided, server device 280 maydetermine whether a time or a location from which the user device 270requests the content is restricted. For example, the request may includeinformation on the time and/or the location of user device 270. Serverdevice 280 may use the account data structure to determine whether thetime or the location is included in a restricted time period and/or arestricted location. If the time or the location is restricted, serverdevice 280 may determine that the content may not be provided to userdevice 270.

As further shown in FIG. 6, process 600 may include obtaining thecontent associated with the download account (block 630). For example,server device 280 may obtain the content if server device 280 determinesat block 625 that the content may be provided to user device 270. Therequest may include information identifying the content. Server device280 may search the account data structure for the content informationcorresponding to the content identified in the request. The contentinformation may identify a location in a memory of server device 280and/or a location in storage device 290 where the content information isstored. Server device 280 may then obtain the content from the memory ofserver device 280 and/or storage device 290 using the contentinformation.

As further shown in FIG. 6, process 600 may include providing thecontent to user device 270 via operator network 210 (block 635). Forexample, server device 280 may provide the content to operator network210 for transmission to user device 270 over a logical connection (i.e.,a PDN connection) created by operator network 210 using the access pointassociated with the download account.

As further shown in FIG. 6, process 600 may include receiving thecontent from server device 280 for forwarding to user device 270 (block640). For example, operator network 210 may receive the content fromserver device 280 to transmit to user device 270.

As further shown in FIG. 6, process 600 may include charging an accountdata plan associated with the download account for data used to providethe content to user device 270 (block 645). For example, operatornetwork 210 may charge the account data plan for the data used toprovide the content to user device 270. Additionally, or alternatively,operator network 210 may charge the member's operator network data planif the account data plan is not used to pay for all the data used toprovide the content. In some implementations, operator network 210 maycharge the member's operator network data plan for roaming charges ifapplicable.

Operator network 210 (e.g., PGW 250) may establish that the memberdevice is obtaining the content from server device 280 over the accesspoint associated with the download account at PGW 250. PGW 250 may senda credit control request to the PCRF and receive a credit control answerindicating a value that should be included in a used service unit forthe account data plan and the member's operator network data plan.Accordingly, the account data plan may be charged for some or all of thedata used to provide the content to user device 270 and the member'soperator network data plan can be charged for the remainder, if any.

As further shown in FIG. 6, process 600 may include forwarding thecontent to user device 270 (block 650). For example, operator network210 may provide or forward the content to user device 270. Accordingly,user device 270 may receive the content.

As further shown in FIG. 6, process 600 may include providing accountdata plan information to server device 280 (block 655). For example,operator network 210 may provide account data plan information to serverdevice 280. The account data plan information may include information onthe data used over the access point by the authenticated downloadaccount members in the operator network 210 and a charge associated withthe data. For example, the account data plan information may indicatethat 1 GB of data was used over the access point and 1 GB of data wascharged to the account data plan between server device 280 and networkoperator 210. For instance, if operator network A operates server device280, operator network B may inform operator network A of an amount ofdata used over the access point by members in operator network B, andoperator network A may pay operator network B for the data according toexisting agreements. In some implementations, the account data planinformation may be provided to server device 280 at predetermined times(e.g., hourly, daily, weekly, etc.). Additionally, or alternatively, theaccount data plan information may indicate an amount of data used peruser and/or an aggregated amount of data used by more than one user.

As further shown in FIG. 6, process 600 may include receiving theaccount data plan information from operator network 210 (block 660). Forexample, server device 280 may receive the account data plan informationfrom operator network 210.

As further shown in FIG. 6, process 600 may include charging a shareddata plan for the download account based on the account data planinformation (block 665). For example, server device 280 may charge orupdate the shared data plan based on the account data plan information.In some implementations, server device 280 may receive account data planinformation from more than one operator network 210, and update theshared data plan based on the account data plan information frommultiple operator networks 210. Accordingly, members may share theshared data plan independent of the members' affiliations with operatornetworks 210.

In some implementations, server device 280 may subtract an amount ofdata from the shared data plan limit based on the amount of data used bymembers on the affiliated operator networks 210. For example, if thedownload account is associated with a pre-paid plan with a predeterminedamount of data, the amount of data remaining in the shared data plan maybe updated by subtracting an amount of data used by members on operatornetworks 210.

In some implementations, server device 280 may add the amount of dataused by members on the affiliated operator networks 210 and calculate atotal amount of data used. For example, if the shared data plan is apost-paid plan, server device 280 may charge for the total amount ofdata used.

In some implementations, server device 280 may allow the account creatorand/or members to access information on the status of the downloadaccount. For example, server device 280 may send a message to theaccount creator and/or one or more other members and/or allow access toa web site indicating the status of the shared data plan (e.g., amountof data remaining).

User device 270 may use the application to obtain the content fromserver device 280 using other networks than operator network 210. Forexample, user device 270 may use a public or home Wi-Fi connectionand/or another access network to connect to server device 280 vianetwork 295. In such a case, user device 270 may not be charged for thedata used over the Wi-Fi connection to obtain the content and the shareddata plan for the download account may not be charged for contentacquired by user device 270.

In some implementations, server device 280 may terminate the downloadaccount. For example, the account creator may request server device 280to terminate the download account. Additionally, or alternatively,server device 280 may terminate the download account because the shareddata plan may have reached the predetermined limit and/or a length oftime set for the download account has expired. Server device 280 mayterminate the download account by deleting the content associated withthe download account and deleting the download account entry in theaccount data structure.

While a series of blocks has been described with regard to FIG. 6, theblocks and/or the order of the blocks may be modified in someimplementations. Additionally, or alternatively, non-dependent blocksmay be performed in parallel.

FIGS. 7A and 7B are diagrams of an example implementation 700 relatingto process 600 shown in FIG. 6. Assume in example implementation 700, anaccount creator wants to allow attendees of a wedding to downloadpictures taken at the wedding without the attendees' data plansincurring high data costs. Assume the account creator requests a serverdevice to create a download account including a shared data plan with alimit of 500 megabytes (MB). Further, assume the account creatordesignates two download account members, member A and member B. Theaccount creator may upload content to the download account and maydesignate that member A and/or member B may upload content to thedownload account. Also, assume member A uses a user device 710, isaffiliated with an operator network A, and has all data paid for by theshared data plan. Further, assume member B uses a user device 720, isaffiliated with an operator network B, and has two thirds of data paidfor by the shared data plan.

As shown in FIG. 7A, member A uses user device 710 to download a photofrom the server device via operator network A. User device 710 receives15 MB of data over operator network A to obtain the photo. However,member A's data plan with operator network A is not charged for any ofthe data. Instead, the shared data plan associated with the downloadaccount is charged for 15 MB of data.

As shown in FIG. 7A, member B uses user device 720 to download a photofrom the server device via operator network B. User device 720 receives15 MB of data over operator network B to obtain the photo. However,member B's data plan with operator network B is only charged for a thirdof the data (i.e., 5 MB). On the other hand, the shared data planassociated with the download account is charged for two thirds of thedata (e.g., 10 MB).

As shown in FIG. 7B, an account creator and/or members A and B mayaccess a website indicating a download account status. For example, thedownload account status may include the amount of data used by eachmember of the download account. For instance, the download accountstatus may indicate that member A has used 15 MB of the shared data planand that member B has used 10 MB of the shared data plan. The downloadaccount status may also indicate that 475 MB of the original 500 MB areremaining in the shared data plan.

Implementations described herein may allow members of a download accountto share a data plan to download content associated with the downloadaccount independent of operator network affiliations.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

To the extent the aforementioned implementations collect, store, oremploy personal information provided by individuals, it should beunderstood that such information shall be used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage, and use of such information maybe subject to consent of the individual to such activity, for example,through “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in conjunction withthresholds. As used herein, satisfying a threshold may refer to a valuebeing greater than the threshold, more than the threshold, higher thanthe threshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

Certain user interfaces have been described herein. In someimplementations, the user interfaces may be customizable by a user or adevice. Additionally, or alternatively, the user interfaces may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interfaces are displayed, ora set of configurations based on capabilities and/or specificationsassociated with a device on which the user interfaces are displayed.

It will be apparent that systems and/or methods, as described herein,may be implemented in many different forms of software, firmware, andhardware in the implementations illustrated in the figures. The actualsoftware code or specialized control hardware used to implement thesesystems and/or methods is not limiting of the implementations. Thus, theoperation and behavior of the systems and/or methods were describedwithout reference to the specific software code—it being understood thatsoftware and control hardware can be designed to implement the systemsand/or methods based on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Where onlyone item is intended, the term “one” or similar language is used.Further, the phrase “based on” is intended to mean “based, at least inpart, on” unless explicitly stated otherwise.

What is claimed is:
 1. A server device, comprising: one or moreprocessors to: store content accessible by the server device, the serverdevice including information identifying a shared data plan, the shareddata plan being updated based on data used on an operator network toprovide the content, from the server device, to one or more users thatare members of the shared data plan; receive a request for the contentfrom a user device associated with a user of the one or more users;provide the content to the user device based on receiving the request;and update, based on a particular amount of data used to provide thecontent from the server device to the user device, the shared data planto indicate that the particular amount of data has been used, the shareddata plan being updated without a data plan, between the user device andthe operator network, being updated, and the shared data plan beingdifferent than the data plan between the user device and the operatornetwork.
 2. The server device of claim 1, where the one or moreprocessors are further to: receive, from the operator network,information indicating the particular amount of data used to provide thecontent from the server device to the user device; and where the one ormore processors, when updating the shared data plan, are to: update theshared data plan based on the information indicating the particularamount of data used to provide the content.
 3. The server device ofclaim 1, where the one or more processors, when updating the shared dataplan, are to: update the shared data plan by subtracting the particularamount of data from a limit of the shared data plan.
 4. The serverdevice of claim 1, where the one or more processors, when updating theshared data plan, are to: update the shared data plan by adding theparticular amount of data to an amount of data used by the members. 5.The server device of claim 1, where the request is received via anapplication on the user device.
 6. The server device of claim 1, wherethe one or more processors are further to: provide, to the operatornetwork, information on authenticated members associated with the shareddata plan.
 7. The server device of claim 1, where the one or moreprocessors are further to: determine whether a data limit of the shareddata plan has been reached; and where the one or more processors, whenproviding the content to the user device, are to: selectively providethe content to the user device based on determining that the data limithas not been reached, the content not being provided based ondetermining that the data limit has been reached.
 8. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by a processorof a server device, cause the processor to: store content accessible bythe server device, the server device including information identifying ashared data plan, the shared data plan being updated based on data usedon an operator network to provide the content, from the server device,to one or more users that are members of the shared data plan; receive,via the operator network, a request for the content from a user deviceassociated with a user of the one or more users; provide, via theoperator network, the content to the user device based on receiving therequest; and update, based on a particular amount of data used toprovide the content from the server device to the user device, theshared data plan to indicate that the particular amount of data has beenused, the shared data plan being updated without a data plan, betweenthe user device and the operator network, being updated, and the shareddata plan being different than the data plan between the user device andthe operator network.
 9. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions that, when executed by theprocessor, further cause the processor to: determine whether the user isauthorized to receive the content; and where the one or moreinstructions, that cause the processor to provide the content to theuser device, cause the processor to: provide the content to the userdevice based on determining that the user is authorized to receive thecontent.
 10. The non-transitory computer-readable medium of claim 8,where the one or more instructions that, when executed by the processor,further cause the processor to: determine whether the user has reached apredetermined data limit; and where the one or more instructions, thatcause the processor to provide the content to the user device, cause theprocessor to: provide the content to the user device based ondetermining that the user has not reached the predetermined data limit.11. The non-transitory computer-readable medium of claim 8, where theone or more instructions that, when executed by the processor, furthercause the processor to: determine whether a download account associatedwith the shared data plan has exceeded a time limit; and where the oneor more instructions, that cause the processor to provide the content tothe user device, cause the processor to: provide the content to the userdevice based on determining that the download account has not exceededthe time limit.
 12. The non-transitory computer-readable medium of claim8, where the one or more instructions that, when executed by theprocessor, further cause the processor to: determine a location at whichthe user device is located; and determine that the location is not arestricted location to which the content is restricted; and where theone or more instructions, that cause the processor to provide thecontent to the user device, cause the processor to: provide the contentto the user device based on determining that the location is not arestricted location.
 13. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions that, when executed by theprocessor, further cause the processor to: determine that the shareddata plan has reached a predetermined limit; and terminate a downloadaccount associated with the shared data plan based on determining theshared data plan has reached the predetermined limit.
 14. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions that, when executed by the processor, further causethe processor to: provide, to the operator network, informationindicating that the user is authorized to use an access point associatedwith a download account.
 15. A method, comprising: storing, by a serverdevice, content, the server device including information identifying ashared data plan, the shared data plan being updated based on data usedto provide the content, from the server device, to one or more usersthat are members of the shared data plan; receiving, by the serverdevice, a request for the content from a user device associated with auser of the one or more users; providing, by the server device, thecontent to the user device; and updating, by the server device and basedon a particular amount of data used to provide the content from theserver device to the user device, the shared data plan to indicate thatthe particular amount of data has been used, the shared data plan beingupdated without a data plan of the user device being updated, and theshared data plan being different than the data plan of the user device.16. The method of claim 15, where the user device is a first userdevice, the request is a first request, the content is first content,and the particular amount of data is a first particular amount of data;and where the method further comprises: receiving a second request forsecond content from a second user device; providing the second contentto the second user device based on receiving the second request; andupdating, based on a second particular amount of data used to providethe second content to the second user device, the shared data plan toindicate that the second particular amount of data has been used, theshared data plan being updated without a data plan of the second userdevice being updated.
 17. The method of claim 15, further comprising:sending a message to the user, the message indicating an amount of dataremaining in the shared data plan.
 18. The method of claim 15, furthercomprising: determining that the shared data plan has reached a timelimit; and terminating the shared data plan based on the determiningthat the shared data plan has reached the time limit.
 19. The method ofclaim 15, further comprising: determining whether the user device hasreached a predetermined data limit; and where providing the content tothe user device comprises: providing the content to the user devicebased on determining that the user device has not reached thepredetermined data limit.
 20. The method of claim 15, where the userdevice is a first user device; where providing the content to the firstuser device comprises: providing, via a first operator network, thecontent to the first user device; where the method further comprises:providing, via a second operator network, the content to a second userdevice; and where updating the shared data plan comprises: updating theshared data plan based on providing the content to the first user deviceand based on providing the content to the second user device.